----- Original Message -----

From: Tom Kerekes tk@... [DynoMotion]

To: DynoMotion@yahoogroups.com

Sent: Thursday, August 27, 2015 1:20 AM

Subject: Re: [DynoMotion] Re: Mach3 Lathe threading followup

 

Hi Tapio,

I can't think of why there would be a delay.   Maybe some Spindle on/off delay?

Can you post your G Code and Mach3 XML Configuration

Regards

TK

Group: DynoMotion	Message: 12167	From: Tom Kerekes	Date: 8/27/2015
Subject: Re: Mach3 Lathe threading followup

Hi Tapio, I'm not sure if there would be delay or not in Mach3 after an M Code anyway. Why not use KMotionCNC?  :} The two G32's in the Demo are showing how multiple G32's can be blended and remain synchronized in KMotonCNC.  The pull out motion is at 45 degrees and feed rate is increased to maintain the same Thread pitch.  With Mach3 that doesn't seem possible. https://youtu.be/B-1TtrbAfwc Regards TK Group: DynoMotion Message: 12168 From: Steve Blackmore Date: 8/27/2015 Subject: Re: Mach3 Lathe threading followup On Fri, 28 Aug 2015 02:05:26 +0000 (UTC), you wrote: >Hi Tapio, >I'm not sure if there would be delay or not in Mach3 after an M Code anyway. >Why not use KMotionCNC?  :} >The two G32's in the Demo are showing how multiple G32's can be blended and remain synchronized in KMotonCNC.  The pull out motion is at 45 degrees and feed rate is increased to maintain the same Thread pitch.  With Mach3 that doesn't seem possible. It is, but why? The pull out is normally done at G0, even when tapered, as is the return to start position. There is then usually a small delay as the index is picked up again for the start of the next pass. The delay can be noticeable if a very slow spindle speed is used and the index point has just been passed, program has to wait for next index point before commencing motion. By slow I mean anything under 500 rpm I don't see any significant delays as I don't use G1 or G3 for the pull out and I've cut many hundreds of thousands of threads with Mach. Steve Blackmore -- Group: DynoMotion Message: 12170 From: Moray Cuthill Date: 8/28/2015 Subject: Re: Mach3 Lathe threading followup I've noticed this problem as well, however I rarely thread on the CNC lathe, so it's not really a problem for me. One thing I have noticed when I have cut threads, is after the threading move, although the feed mode changes back from feed/rev to feed/minute, the actual figure stays the same until the pull out move is complete, at which point the correct feed/minute rate is applied. I.e. if I'm cutting say a 2mm pitch thread, the mode in Mach changes to 2mm feed/rev for the threading move, then it switches to 2mm/min for the pull out move, before switching back to the previously set G1 speed prior to the return move (I've never actually noticed if the return move is at G0 or G1 speed). I am planning on moving to KMotionCNC, however I'm currently adopting the "If it isn't broke, don't fix it" methodology, as Mach does what I currently need it to. Moray On Fri, Aug 28, 2015 at 3:05 AM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:   Hi Tapio, I'm not sure if there would be delay or not in Mach3 after an M Code anyway. Why not use KMotionCNC?  :} The two G32's in the Demo are showing how multiple G32's can be blended and remain synchronized in KMotonCNC.  The pull out motion is at 45 degrees and feed rate is increased to maintain the same Thread pitch.  With Mach3 that doesn't seem possible. https://youtu.be/B-1TtrbAfwc Regards TK Group: DynoMotion Message: 12178 From: Tapio Larikka Date: 8/29/2015 Subject: Re: Mach3 Lathe threading followup  Hi Tom,   I uploaded the threading g-code and xml config file along with others here: https://groups.yahoo.com/neo/groups/DynoMotion/files/Tapio/   Delay after M code could be there but that would be 1 delay vs 5 delays when cutting the thread in 5 passes. I cut 16 tpi threads on AISI304 so I don't think I can reduce the number of passes.   Three reasons keep me from moving to KMotionCNC:   - KMotionCNC is the screen layout.  The manual move/jog buttons are (in my opinion) too small, in wrong place and inconviniently grouped for use with touch screen.   For safety and convenience I feel that jog buttons have to be place so that I can operate them with thumb while grabbing support from enclosure side with other fingers.   I didn't have time to take a photo of the controller to explain this better but I'll upload it on Monday   I have keyboard attached only for maintanence and only 3 external buttons for E-Stop, control voltage and cycle start.   - I have a gang tool type lathe setup so I need Y-axis for tool position/slot. - I use 5C collet chuck that is wedge locked/opened by external hydraulic cylinder and this needs Spindle/A-axis positioning for closing/opening.   With KMotionCNC I could move the chuck operation to user c code but the two other reasons would still remain.   I tried to modify the KMotionCNC screen with resource editor but came to solution that task and tool don't match.   As soon as I find time I'll try to see if I get the VS2013 community installed to see if it would easier way to modify KMotionCNC.   Rgds, Tapio     ----- Original Message ----- From: Tom Kerekes tk@... [DynoMotion] To: DynoMotion@yahoogroups.com Sent: Friday, August 28, 2015 5:05 AM Subject: Re: [DynoMotion] Re: Mach3 Lathe threading followup   Hi Tapio, I'm not sure if there would be delay or not in Mach3 after an M Code anyway. Why not use KMotionCNC?  :} The two G32's in the Demo are showing how multiple G32's can be blended and remain synchronized in KMotonCNC.  The pull out motion is at 45 degrees and feed rate is increased to maintain the same Thread pitch.  With Mach3 that doesn't seem possible. https://youtu.be/B-1TtrbAfwc Regards TK Group: DynoMotion Message: 12179 From: Tapio Larikka Date: 8/29/2015 Subject: Re: Mach3 Lathe threading followup Hi Steve,   I cut the threads at 1000 rpm. I think delay at the beginning is part of the operation but the delay at the end shoud have nothing to do with index.   I looks that G32 threading pass and what ever move comes next are paired as thread and pullout so that they work without delay but the delay after pullout persists. So far I have tried G0, G1, G3 and G32 as pullout, all with same results. I also tried G32 thread-G32pullout-G32return to see if the delay would transfer to the end of the return move, but it didn't.   I settled for G3 as machine sounds to run softest this way.   I'm running with Mach43.066 at the moment, but I try rolling back to .062 as soon as I find time.   Rgds, Tapio      Group: DynoMotion Message: 12180 From: Steve Blackmore Date: 8/29/2015 Subject: Re: Mach3 Lathe threading followup On Sat, 29 Aug 2015 13:54:57 +0300, you wrote: >Hi Steve, > >I cut the threads at 1000 rpm. I think delay at the beginning is part of the operation but the delay at the end shoud have nothing to do with index. > >I looks that G32 threading pass and what ever move comes next are paired as thread and pullout so that they work without delay but the delay after pullout persists. >So far I have tried G0, G1, G3 and G32 as pullout, all with same results. >I also tried G32 thread-G32pullout-G32return to see if the delay would transfer to the end of the return move, but it didn't. > >I settled for G3 as machine sounds to run softest this way. > >I'm running with Mach43.066 at the moment, but I try rolling back to .062 as soon as I find time. I run 3.038 Anything after .042 is bug ridden. Steve Blackmore -- Group: DynoMotion Message: 12183 From: Tom Kerekes Date: 8/30/2015 Subject: Re: Mach3 Lathe threading followup Attachments : datauri-file-12183(1).png Hi Tapio, I tried 3.043.066 and I don't really see the delays (other than the spindle sync) The G3 arcs seem to be backwards for some reason. The cycle time for that job is about 32 seconds. Regards TK Group: DynoMotion Message: 12184 From: Tapio Larikka Date: 8/30/2015 Subject: Re: Mach3 Lathe threading followup [1 Attachment]  Hi Tom,   I have Mach3 in 3 different PC's and one of them shows G3 backwards ie " )( " while others show "( )" I get in app32-35 seconds to the M5 command, then some 8 sec to program end.   May well be that this falls in the category "Mach Mysteries".   I think I'll have to work harder toward KMotionCNC, either by vb.net or by VS2013   Big Thank You for bearing with me on this topic :)   Rgds, Tapio   ----- Original Message ----- From: Tom Kerekes tk@... [DynoMotion] To: DynoMotion@yahoogroups.com Sent: Sunday, August 30, 2015 10:14 PM Subject: Re: [DynoMotion] Re: Mach3 Lathe threading followup [1 Attachment]   Hi Tapio, I tried 3.043.066 and I don't really see the delays (other than the spindle sync) The G3 arcs seem to be backwards for some reason. The cycl e time for that job is about 32 seconds. Regards TK Group: DynoMotion Message: 12185 From: Steve Blackmore Date: 8/30/2015 Subject: Re: Mach3 Lathe threading followup On Mon, 31 Aug 2015 00:14:25 +0300, you wrote: >Hi Tom, > >I have Mach3 in 3 different PC's and one of them shows G3 backwards ie " )( " while others show "( )" >I get in app32-35 seconds to the M5 command, then some 8 sec to program end. Think about that - You are in XZ plane on a lathe - not XY ;) Steve Blackmore -- Group: DynoMotion Message: 12186 From: Steve Blackmore Date: 8/30/2015 Subject: Re: Mach3 Lathe threading followup [1 Attachment] On Sun, 30 Aug 2015 19:14:03 +0000 (UTC), you wrote: >Hi Tapio, >I tried 3.043.066 and I don't really see the delays (other than the spindle sync) >The G3 arcs seem to be backwards for some reason. You sure? Here's something I wrote in the Mach forum back in 2009 <G>. Arcs are reversed for a front tool post. Think about it, in the XZ plane a G2 goes anticlockwise from the operators point of view stood in front of the lathe. To get the same viewpoint as a mill you'd have lie underneath it, feet out, looking up :) Steve Blackmore -- Group: DynoMotion Message: 12187 From: Tapio Larikka Date: 8/31/2015 Subject: Re: Mach3 Lathe threading followup Hi Steve,   The "Arcs are reversed..." sounds familiar. I remember reading it somewhere else also. Now I finally understand the meaning of it :)   Tapio